Add server TLS key and cert into Che configmap if a separate namespace for Che workspaces is configured #421
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Mykola Morhun mmorhun@redhat.com
What does this PR do
If Eclipse Che is configured to use a separate namespace for Che workspaces via
CHE_INFRA_KUBERNETES_NAMESPACE_DEFAULT
Che property, then add into Che config map Che server TLS secret (key and certificate) in order for Che server to be able to configure workspace components with right TLS key and certificate (as it is not possible to access Che server TLS secret from a separate namespace) .Which issues this PR resolves
eclipse-che/che#17631